fix(history): restore attachments during session replay#297
Open
Orcaryn wants to merge 1 commit into
Open
Conversation
Orcaryn
marked this pull request as ready for review
July 14, 2026 12:12
Orcaryn
force-pushed
the
chapeta/history-attachments
branch
from
July 21, 2026 16:01
8e41c9c to
22546c5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root cause
Codex stores attachment context as synthetic prompt text plus structured
UserInputentries. Duringsession/load, embedded images and available local images were replayed as text links, file mentions were dropped, and the synthetic wrapper was exposed verbatim. When response-item fallback recovery was active, it also replayed the raw user message and image reference alongside the authoritative thread history.Validation
npm test— 314 passed, 28 skippednpm run typechecknpm run build